LTE IoT 4 Click

NOTE: The GPS functionality in the SiP firmware is not currently supported. However, the user can develop their FW using Nordic's SDK, the nRF Connect SDK, and update the SiP using the SWD interface.

LTE IoT 4 Click is based on the nRF9160, a compact, highly-integrated System-in-Package (SiP) with integrated ARM® Cortex®-M33 processor, multimode LTE-M/ NB-IoT modem, RF front end (RFFE), GPS, and power management from Nordic Semiconductor. ARM® Cortex®-M33 processor is supported by 1MB of Flash and 256KB RAM memory with advanced security features, like Arm CryptoCell that enhances security by offering cryptographic and security resources to help to protect your IoT applications from various attack threats. It also has built-in assisted GPS suitable for tracking applications that combines location data from the Cloud with GPS satellite to allow remote monitoring of the device position. The nRF9160 is certified to operate in the most important regions, networks, and LTE bands around the world.

The nRF9160 is specifically designed to take full advantage of the energy efficiency associated with the LTE-M and NB-IoT standards. It supports both the PSM and eDRX power-saving modes, enabling the nRF9160 to sleep for a longer period. At the left side of this Click board™, there is an additional header, labeled as SWD, which offers full support of debugging and programming capabilities through the serial wire debug (SWD) interface (SWDIO, SWCLK, and SWO).

LTE IoT 4 Click communicates with MCU using the UART interface as its default communication protocol with the option for the users to use other interfaces such as SPI and I2C if they want to configure the module and write the library by themselves using these protocols. It also can be reset through the Hardware Reset pin, labeled as RST on the mikroBUS™ socket, by putting this pin in a logic low state.

The LTE modem integrates a very flexible transceiver that supports frequency range from 700 to 2200 MHz. Also, it possesses two SMA antenna connectors with an impedance of 50Ω, labeled as GPS and LTE, used for connecting the appropriate antenna that Mikroe has in its offer. Besides those SMA connectors, this Click board™ also has a nano-SIM card slot that provides multiple connections and interface options.

This Click board™ is designed to be operated only with a 3.3V logic voltage level. A proper logic voltage level conversion should be performed before the Click board™ is used with MCUs with different logic levels. However, the Click board™ comes equipped with a library that contains functions and an example code that can be used, as a reference, for further development.

Specifications:

PinOut Diagram:

This table shows how the pinout on LTE IoT 4 Click corresponds to the pinout on the mikroBUS™ socket (the latter shown in the two middle columns).

Notes	Pin					Pin	Notes
	NC	1	AN	PWM	16	NC
Reset	RST	2	RST	INT	15	NC
SPI Chip Select	CS	3	CS	RX	14	TX	UART TX
SPI Clock	SCK	4	SCK	TX	13	RX	UART RX
SPI Data OUT	SDO	5	MISO	SCL	12	SCL	I2C Clock
SPI Data IN	SDI	6	MOSI	SDA	11	SDA	I2C Data
Power Supply	3.3V	7	3.3V	5V	10	NC
Ground	GND	8	GND	GND	9	GND	Ground

OnBoard Settings And Indicators:

LTE IOT 4 Click Electrical Specifications:

Software Support:

We provide a library for the LTE IoT 4 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on mikroE github account.

Library Description

This library contains API for LTE IoT 4 Click driver.

Key functions:

• void lteiot4_cfg_setup ( lteiot4_cfg_t *cfg );  - Config Object Initialization function.
• LTEIOT4_RETVAL lteiot4_init ( lteiot4_t *ctx, lteiot4_cfg_t *cfg );  - Initialization function.
• void lteiot4_default_cfg ( lteiot4_t *ctx );  - Click Default Configuration function.

Examples description

This example reads and processes data from LTE IoT 4 Click boards™.

The demo application is composed of two sections :

void application_task ( void )
{
    if ( app_connection_status == WAIT_FOR_CONNECTION )
    {
        //CEREG
        log_info( &logger, " Check connection  " );
        lteiot4_send_cmd( &lteiot4, LTEIOT4_CMD_CHECK_CONNECTION );
        app_error_flag = lteiot4_rsp_check();
        lteiot4_error_check( app_error_flag );
        Delay_ms( 500 );
        
        //CEREG
        log_info( &logger, " Check network status  " );
        lteiot4_send_cmd( &lteiot4, LTEIOT4_CMD_CHECK_REGISTARTION );
        app_error_flag = lteiot4_rsp_check();
        lteiot4_error_check( app_error_flag );
        Delay_ms( 500 );
        
        //CEREG
        log_info( &logger, " Check signal quality  " );
        lteiot4_send_cmd( &lteiot4, LTEIOT4_CMD_SIGNAL_QUALITY );
        app_error_flag = lteiot4_rsp_check();
        lteiot4_error_check( app_error_flag );
        log_printf( &logger, "-------------------------------rn" );
        Delay_ms( 5000 );
    }
    else
    {
        log_info( &logger, "CONNECTED TO NETWORKrn" );
        log_printf( &logger, "-------------------------------rn" );
        //CCLK
        log_info( &logger, " Set Time " );
        lteiot4_send_cmd( &lteiot4, LTEIOT4_CMD_SET_DUMMY_CLOCK );
        app_error_flag = lteiot4_rsp_check();
        lteiot4_error_check( app_error_flag );
        log_printf( &logger, "-------------------------------rn" );
        Delay_ms( 3000 );
        
        for(;;)
        {
            //XTEMP
            log_info( &logger, " Check Temperature " );
            lteiot4_send_cmd( &lteiot4, LTEIOT4_CMD_CHECK_TEMPERATURE );
            app_error_flag = lteiot4_rsp_check();
            lteiot4_error_check( app_error_flag );
            Delay_ms( 500 );
            //CCLK
            log_info( &logger, " Check Time " );
            lteiot4_send_cmd( &lteiot4, LTEIOT4_CMD_CHECK_CLOCK );
            app_error_flag = lteiot4_rsp_check();
            lteiot4_error_check( app_error_flag );
            log_printf( &logger, "-------------------------------rn" );
            Delay_ms( 5000 );
        }
    }
}

The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on mikroE github account.

Other mikroE Libraries used in the example:

• MikroSDK.Board
• MikroSDK.Log
• Click.LTEIoT4

Additional notes and informations

Depending on the development board you are using, you may need USB UART click, USB UART 2 click or RS232 click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all MikroElektronika compilers, or any other terminal application of your choice, can be used to read the message.

MikroSDK:

This Click board™ is supported with mikroSDK - MikroElektronika Software Development Kit. To ensure proper operation of mikroSDK compliant Click board™ demo applications, mikroSDK should be downloaded from the LibStock and installed for the compiler you are using.

For more information about mikroSDK, visit the official page.